Deployable tag management in computer data networks

ABSTRACT

A tag management system in a computer data network can be used to manage one or more tag configurations with templates. A template may enable efficient tag configuration by causing presentation of an improved user interface that facilitates user-specified mappings between a custom content site and predefined tag management attributes. By completing a template, which may depend on other templates or have templates that depend on it, the tag management system can automatically deploy complex tag management configurations to track end user interactions over a data network.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright ownerunderstands that the patent document or the patent disclosure, as itappears in the Patent and Trademark Office patent file or records, maybe used in the ordinary course of business or transactions with thePatent and Trademark Office, but hereby reserves all copyright rightswhatsoever.

RELATED APPLICATIONS

Any and all applications for which a foreign or domestic priority claimis identified in the Application Data Sheet as filed with the presentapplication are hereby incorporated by reference under 37 CFR 1.57.

BACKGROUND

Some operators of content sites, such as websites, can obtain theresults of analytics performed with regard to user interactions on theircontent sites. User analytics can include any type of data regardinginteractions of end users with content sites, among other types of data.There are different approaches to gathering analytics data, one of whichincludes employing the use of tags.

Tags can include small pieces of website code that allow a websiteoperator to measure traffic and visitor. Adding tags to a content sitehas typically required involving a developer to manually insert tag codeinto one or more pages of a website.

BRIEF DESCRIPTION OF THE DRAWINGS

Throughout the drawings, reference numbers are re-used to indicatecorrespondence between referenced elements. The drawings are provided toillustrate embodiments of the features described herein and not to limitthe scope thereof.

FIG. 1 depicts an embodiment of a computing environment that providesaccess to an analytics system including a template distribution system,a visitor processing system, or a tag management system.

FIG. 2 depicts an embodiment of a template implementation process.

FIG. 3 depicts an embodiment of a tag management dependency process.

FIG. 4 depicts an embodiment of a template distribution process.

FIGS. 5-7, 8A, 8B, 9-17, 18A, 18B, and 19-24 depict example tagmanagement configuration-related user interfaces.

FIGS. 25A, 25B, 25C, 25D, 25E, 25F, 25G, 25H, and 25I depict exampleuser interfaces corresponding to a template implementation process.

FIGS. 26A, 26B, and 26C depict example user interfaces followingimplementation of one or more templates.

FIGS. 27A, 27B, 27C, 27D, 27E, 27F, 27G, 27H, 27I, 27J, 27K, 27L, and27M depict example user interfaces corresponding to another templateimplementation process.

FIG. 28 depicts an example user interface to display implementedtemplates, tag management objects, or visualizations.

FIG. 29 depicts an example template object.

FIG. 30 depicts an example template attribute and an example templateoperator.

FIG. 31 depicts an example template transformation and an exampletemplate rule.

FIG. 32 depicts an example template audience and an example templatecollection.

FIG. 33 illustrates an analytics system configuration on which may beimplemented various embodiments of systems and methods in accordancewith the disclosure.

DETAILED DESCRIPTION I. Tag Management Introduction

Tag management systems can be used to configure tags of a content siteor to manage those tags. In one embodiment, a tag management system candeploy a single tag or a tag container to a content site or networkpages of a content site. Each page or any subset of web pages in thecontent site can incorporate the tag container as a universal tag thatcan be used to gather any type of end user interaction. This tagcontainer can be used to interface with any number of third party vendortags without requiring, in certain embodiments, such tags to be codedexpressly in the code of the web pages of the content site. Thus,changes to the tagging of a content site may be made through a userinterface provided by the tag management system without having to use adeveloper to add the tags to the web pages manually. Despite theefficacy of a tag management system for configuration users without ITor programming knowledge, it may be advantageous to further automate thedeployment of complex tag management configurations.

II. Tag Management Templates

The present disclosure describes embodiments, systems, methods, andnon-transitory computer readable media that can address the complexitiesof tag management configuration. For example, there may be general tagmanagement patterns that are usable across multiple different contentsites to perform various functions such as tracking end userinteractions. However, the implementation of such patterns may requirethe configuration of many tag management attributes or instructions thatmay be difficult or time consuming to configure, or the configurationuser may not be aware of such patterns. While a tag management patternmay be applicable to multiple content sites, each content site mayrequire custom configuration due to content site differences such asdifferences in uniform resource identifier patterns or variables orparameters of those uniform resource identifier patterns. Accordingly, atemplate object may include the instructions to perform the tagmanagement configuration. A template object may also include one or moreprompts configured to be presented to a configuration user. A tagmanagement system may use the user input responses to the prompts andthe template object to generate output that configures the tagmanagement system. A tag distribution system may also control thedistribution, version control, or access to template objects toconfiguration users or accounts.

In some embodiments, an advantage of the systems and techniquesdescribed herein can include more efficient tag management configurationthrough templates. For example, the template objects may be configuredor curated with one or more dependencies. In the example, a firsttemplate object may include many base configurations that facilitatenear completion or completion of second template objects. Additionallyor alternatively to the ability of template objects to receiveconfiguration user input, the template objects may include conditionalinstructions or may allow the configuration user to provide conditionalinstructions. Thus, instead of a configuration user needing months oryears to learn effective tag management patterns, those effectivepatterns can be embedded within the template objects. Accordingly, asopposed to lower level configurations that may be difficult forconfiguration users to set up, understand, or explore, a template objectmay be a higher level data container that configuration users canexplore, add, remove, or update within the tag management system.

The systems and techniques described herein may be intrinsically tied tonetwork and/or computer technology because such solutions are related totags and the tag management of network content sites such as websites.For example, the tag management deployment techniques described hereinmay configure a tag management system to analyze captured network data.Example network data includes HTTP data and uniform resource identifierdata (such as uniform resource locators (“URLs”)) that are intrinsicallytied to computer technology.

The systems and techniques described herein may improve computertechnology. For example, as described herein, a tag managementimplementation may require the configuration of many tag managementattributes or instructions that may be difficult or time consuming toconfigure, or the configuration user may unable to complete theconfiguration properly. The template objects may contain rules thatautomatically configure a tag management system. Accordingly, thesystems and techniques described herein may enable rapid deployment orconfiguration of a tag management system through the use of templateobjects. Further, the implementation of template objects may deploy tagmanagement configurations in a predetermined or memory-efficient manner,which reduces superfluous or redundant manual configurations, such asthose that may arise from human error, thereby reducing memoryrequirements. Further, the template objects may be viewable in animproved graphical user interface. Accordingly, an improved graphicaluser interface may enable faster setup times of configurations. Theimproved graphical user interfaces may also enable improvement in usersearch times of tag management configurations since an example templateobject represents a logical grouping of configurations that wouldotherwise be difficult for a configuration user to search or reviewwithout the user-friendly logical grouping.

As used herein, in addition to having its ordinary meaning, a “templateobject” refers to a data object associated with the configuration of thetag management system. The template object may configure user interfacesof the tag management system to present prompts and receive user inputfrom a configuration user. A template object may include components.Example components include attributes, rules, transformations,instructions, operators, or audiences, as described herein. Rules,transformations, or audiences may include instruction sets. Thecompletion of an implementation process associated with the templateobject may output attributes, an audience, or an action connector, asdescribed herein. A tag management object may be generated by thecompletion of the template process. A tag management object maycorrespond to the inputs and outputs of a completed template object. Thetag management system may also generate visualizations corresponding tothe implemented templates. For example, the visualizations may report onthe performance of an implemented template. Template objects may becurated by administrators or analysts that have the appropriateknowledge to configure such objects. The terms “template,” “templateobject,” and “play” may be used interchangeably in the presentdisclosure. As used herein, “workflow” may refer to the process ofpresenting user interfaces associated with a template object or theimplementation of a template object.

As used herein, in addition to having its ordinary meaning, an“audience” may refer to a collection of end user such as a specificgroup of end users or visitor attributes. Audiences may be usefulbecause the collection of end users may be targeted in some way.Audiences that are generated from a template can be acted on via actionconnectors.

As used herein, in addition to having its ordinary meaning, an “actionconnector” may refer to an integration between the tag management systemand a third-party vendor. An example action connector includes arecipient such as a vendor. The example action connector may specifysending audience data or other interaction data to the recipient. Atemplate that generates connectors will setup appropriate actions thatmay be configured with the data that can be sent to the vendor includingan audience that the connector may be targeting. The terms “actionconnector” and “connector” may be used interchangeably in the presentdisclosure.

As used herein, in addition to having its ordinary meaning, an “enduser” may refer to a user of a content site. The terms “end user” and“visitor” may be used interchangeably in the present disclosure. As usedherein, in addition to having its ordinary meaning, a “configurationuser” may refer to a user of the tag management system. The terms“configuration user,” “analytics user,” and “tag management user” may beused interchangeably in the present disclosure.

III. Example Tag Management Template System Processes

FIG. 1 illustrates a computing environment 100 for implementing varioustag features, including some or all of the tag management features orend user processing features described herein. In the computingenvironment 100, an end user system 102 communicates over a network 108with a site server 110. The end user system 102 can include any form ofcomputing device and may be a desktop, laptop, smartphone, tablet, orthe like. A browser 103 or other application software installed in theend user system 102 accesses one or more content pages of a content sitestored in content pages storage 112 of the site server 110. The contentpages can be files that may be accessed remotely and provided to the enduser system 102. Accordingly, the content pages may be web pages,documents (such as pdf documents), videos, images, text, combinations ofthe same, or the like. The site server 110 may be a web server, anapplication server, a database server, combinations of the same, or thelike. Further, the network 108 can include a local area network (LAN), awide area network (WAN), a company intranet, the public Internet,combinations of the same, or the like.

As shown, one or more content pages 112 of the content site 110 caninclude a tag container 114. The tag container 114 can be an example ofthe tag container described above and can be a universal tag that isinstalled or incorporated in one or more content pages 112 in place of,or instead of, incorporating numerous tags in each page. The tagcontainer 114 can communicate with one or more data collection tagsimplemented on one or more tag servers 120. The data collection tags caninclude third party tags provided by tag vendors that are differententities than an operator of, or provider of, the tag container 114. Inaddition, the tags can include a visitor tag or tags that can beprovided by the same provider as the provider of the tag container 114(or a different provider in some embodiments). Tags and tag containersare described in detail in U.S. Pat. No. 8,805,946, titled “SYSTEM ANDMETHOD FOR COMBINING CONTENT SITE VISITOR PROFILES,” which isincorporated by reference herein in its entirety.

The tag management system 140 can enable analytics users (describedherein) to configure the types of data tracked for different visitors ofthe content site 110, as well as analyze and report on this visitordata. For instance, in one embodiment, the tag management system 140 canprovide one or more user interfaces that enable customization ofcollecting information about visitors to the content site 110. Thisinformation can be obtained initially by the visitor tag(s), which maybe provided through the tag container 114 to the end user system 102 forexecution in the browser 103. Upon execution in the browser 103, thevisitor tag(s) can supply visitor data to the analytics system 130(optionally through the tag servers 120). Such visitor data can bestored in the interaction data storage 160. Analytics users cansubsequently query the interaction data to obtain reports or otherinformation about visitors to the content site 110. Other uses forvisitor profile data are described herein.

The analytics system 130 can include a visitor processing system 142 anda tag management system 140. The visitor processing and tag managementsystems 140, 142 are shown separately for illustrative purposes,although their functionality may be implemented by a single system. Theanalytics system 130 can be implemented without the visitor processingsystem 142, and thus, the functionality of the tag management system 140can be implemented independent of any visitor processing functionality.

The visitor processing system 142 can enable tag management users toconfigure the types of data tracked for different visitors of a contentsite, as well as to analyze and report on this visitor data. Forinstance, the visitor processing system 142 can provide one or more userinterfaces that enable customization of collecting information aboutvisitors to a content site. This information can be obtained initiallyfrom a tag object or one or more tags, which may be provided through thetag server 120 to the end user system 102 for execution in the browser103. Upon execution in the browser 103, the tag object or one or moretags can supply visitor data to the visitor processing system 142(optionally through the tag server 120). Such visitor data can be storedin visitor profiles in the visitor profiles storage 136. Tag managementusers can, for example, subsequently query the visitor profiles toobtain reports or other information about visitors to a content site.

The tag management system 140 can be used to manage the one or more tagsassociated with the content pages stored in the content pages storage112 or the content objects stored in the content objects storage 142.For instance, the tag management system 140 can provide functionalityfor tag management users to select which tags to associate with whichone or more content pages or one or more content objects for a varietyof vendor-specific processing purposes or customize the tags forparticular content pages or content objects. These purposes can includeobtaining analytics for data analysis or business intelligence, trackingaffiliate activity with respect to a content site, obtaining user datafor displaying targeted ads, obtaining user data for customizing searchfunctionality or email campaigns targeted to the end users, obtaininguser data for personalizing content of a content page, obtaining userdata for integration with social networking functionality, obtaininguser data for big data analysis, combinations of the same, or the like.As described herein, the tag management system 140 can further use ortemplate objects to manage or configure the one or more tags. Forexample, the tag management system 140 accesses or template objects fromthe template data storage 162 and presents a user interfacecorresponding to the one or more template objects in the tag managementuser system 104. Accordingly, the tag management system 140 can storethe output of the implementation of the one or more templates in the tagmanagement data storage 164. Further, the template distribution system150 can manage the distribution of the one or more template objects tothe tag management user system 104.

Data collected by the tag object or tags can be provided to the tagvendor systems 170, which can perform any of this vendor-specificprocessing. The data collected or related data may additionally oralternatively be passed to the tag vendor systems 170 through the siteserver 110, the tag server 120, or the analytics system 130. In someembodiments, the tag management system 140 can include a publish enginethat generates or revises tag objects, tags, or tag containers.

A tag management user system 104 can access the tag server 120 or theanalytics system 130 via the network 108. Like the end user system 102,the tag management user system 104 can include a browser 105 or otherapplication software that can access network applications over thenetwork 108. The tag management user system 104 can also be any type ofcomputing device including, but not limited to, a desktop, laptop,tablet, smartphone, or the like. The tag management user system 104 canbe operated by tag management users such as marketing professionals,website operators, business users, operators of a content site or thesite server 110, or any other individual who uses tag objects or tags ordata obtained therefrom. Tag management users are not the end users of acontent site in certain embodiments. The tag management users can usethe tag management user system 104 to dynamically update the types ofdata tracked or analyzed for different visitors of a content site. Inaddition, the tag management user can use the tag management user system104 to customize tag objects or tags for particular content pages orcontent objects.

The computing environment 100 can additionally include more end usersystems and tag management user systems than just the end user system102 and the tag management user system 104 shown in FIG. 1. Multiple enduser systems can thus, for instance, access content pages from the siteserver 110 via the network 108, and multiple tag management user systemscan interact with the analytics system 130 via the network 108.

Turning to FIG. 2, an example template implementation process 200 isshown. The process 200 illustrates an example mode of operation of thecomputing environment 100 and may be implemented by the variouscomponents shown in the computing environment 100. For convenience, theprocess 200 is described in the context of the computing environment100, but may instead be implemented by other systems described herein orother computing systems not shown. The process 200 provides one exampleapproach by which a template object can be implemented. Depending on theembodiment, the method 200 may include fewer or additional blocks and/orthe blocks may be performed in order different than is illustrated.

At block 202, the tag management system 140 accesses a template object.For example, a template object may be accessed from the template datastorage 162. The tag management system 140 may access a template objectbased on a selection by configuration user within the user interface ofthe tag management system 140, such as the example user interfaces 2500or 2700 of FIG. 25A or 27A, respectively. For example, the templateobject may include one or more identifiers that may correspond to one ormore attributes. As described herein, an example attribute includes ahome page attribute that can be used by the tag management system toidentify user interactions with the home page of a content site.

At block 204, the tag management system 140 determines if the templateobject has any prerequisites. The tag management system 140 maydetermine prerequisites based on the inputs of the template object. Asdescribed herein, a template object may include one or more identifiersfor other objects. Accordingly, the tag management system 140 maydetermine prerequisites of template objects, or prerequisites ofprerequisites, etc., using the identifiers. For example, a downstreamtemplate object may include an input attribute “event name”. The “eventname” attribute may be the output of a parent template object.Additionally, the parent template object may have its own prerequisites,which may be determined by the tag management system 140 in a similarmanner. The tag management system 140 may determine whether theprerequisite components or template objects have been assigned values orhave been completed. Accordingly, the tag management system 140 mayreturn to block 202 to recursively access prerequisite template objects,components thereof, or tag management objects. As described herein, thetag management system 140 may prompt users to complete any prerequisitesbefore allowing the configuration user complete the present template.

In some embodiments, the tag management system 140 uses the attributeidentifiers to determine prerequisites. For example, the tag managementsystem 140 determines the prerequisites for a template object byaccessing one or more identifiers of the template object. In theexample, the tag management system 140 then determines another templateobject that also include the one or more identifiers, such as the one ormore identifiers being outputs of the other template object. Thus, thetag management system 140 can dynamically, recursively, or in aprecomputed manner determined the one or more prerequisites ordependencies for a particular template object.

Additionally or alternatively, the tag management system 140 may useother methods for determining prerequisites. For example, templateobjects may include a template identifier and a data structure, such asan array, of prerequisite template identifiers. Accordingly, the tagmanagement system 140 may use the data structure of prerequisitetemplate identifiers to access any prerequisite template objects orcomponents.

At block 206, the tag management system 140 presents user interfacesbased on the template object. The example template objects may includedata to configure the user interfaces of the tag management system 140,which may be described in further detail with respect to the exampletemplate object 2900A-2900B of FIG. 29. The user interfaces presented bythe tag management system 140 may include one or more prompts and userinput elements. In some embodiments, the template object includesinstructions that configure the visual presentation of the prompts anduser input elements. For example, the template object can includeformatting instructions (such as font and font size instructions),presentation layout instructions (such as alignment instructions), andother presentation instructions including color or images to bepresented in the user interface. Example user interfaces correspondingto the template objects are described in further detail with respect toFIGS. 25B through 25I and FIGS. 27B through 27M. For example, a promptmay be presented corresponding to the home page attribute that requestsa user to enter an input value for the home page attribute.

The tag management system 140 may determine if any components of thetemplate object have pre-existing values or are assigned, as describedherein. Accordingly, the tag management system 140 may presentprepopulated values for user input elements where pre-existing valuesexist. An example of a user interface with prepopulated values may bedepicted in FIG. 25C. Additionally or alternatively, the tag managementsystem 140 may suppress prompts or user interface elements based on thedetermination of pre-existing values for corresponding components orattributes of the template object. For example, the tag managementsystem 140 may determine a subset of user interface elements to presentto the user. Continuing with the subset example, the template object mayinclude data regarding one or more user interface or user inputelements. The tag management system 140 may determine a subset of userinterface elements based on the template object components that haveunassigned data values and the components with assigned values may beexcluded or not present within the subset of user interface elements.The tag management system 140 may present the subset user interfaceelements to a configuration user. As described herein, user inputelements may be read only, editable, or editable with a warning, whichmay be defined by the template object.

At block 208, the tag management system 140 receives user input via theuser interfaces. For example, an example prompt of the template objectmay request the user to specify the data value for attribute. Continuingwith a specific example, the prompt may request a data value for a pagetype attribute whereby the user indicates what text string in thecontent site's URL corresponds to the site's checkout page such as thetext “cart” or for the home page, which may be a custom value such as“index.” Example user interfaces corresponding to the receiving userinput via user interfaces are described in further detail with respectto FIGS. 25C through 25G and FIGS. 27C through 27L. For example, asdepicted in FIGS. 25C through 25G and FIGS. 27C through 27L, thetemplate objects may specify prompts and corresponding user interfaceelements in a series until completion.

At block 210, the tag management system 140 generates output based onthe user input. For example, the tag management system 140 may output anattribute with a data value corresponding to the user input. The outputmay be stored in the tag management data storage 164. Continuing with aspecific example, a page type attribute for a checkout page (with thevalue “cart”) may be output to the tag management data storage 164. Asanother example, a home page configuration may be output to the tagmanagement data storage 164 that enables the tag management system toidentify home pages by text in the URL corresponding to “index.”Additional examples of template output include rules, badges, ortransformations. The tag management system 140 may use the identifiersin the template object to evaluate or retrieve the values for theobjects that correspond to the identifiers, as described herein. In someembodiments that do not employ a universal tag, tags may be output bythe completion of the template object. As described herein, the tagmanagement system 140 may use the template object to output audiences orcorresponding action connectors. For example, the template object maycollect end users matching specific criteria into an audience, emailaddresses or other user identifying information may be collected for theaudience members, and the action connector may specify sending theend-user information to a third-party vendor such as an email vendor.The tag management system 140 may generate visualizations associatedwith the completed templates, as described herein.

In some embodiments, some output of a completed template object may benon-editable or edible with a warning. For example, it may beadvantageous to prevent or warn a user about editing or removing anindividual output attribute associated with a template object becausesuch an action may break the tag management functionality represented bythe template or any other configurations associated with the attribute.Accordingly, the tag management system 140 may enable the configurationuser to repeat a template process if the configuration user wants toupdate a value associated with an output, which may advantageouslypreserve the integrity of the tag management configurations.

At block 212, the tag management system 140 generates a tag managementobject based on the user input. For example, the tag management system140 may store a tag management object corresponding to the user inputand elements of the template object to the tag management data storage164. Thus, the tag management system 140 may be able to display to theconfiguration user the completed templates and the collection ofattributes and outputs corresponding to the completed template. In someembodiments, a configuration user may remove a tag management objectfrom the tag management system 140, which may automatically remove allof the outputs associated with the tag management object. Suchfunctionality to automatically remove attributes associated with a tagmanagement object may be advantageous because individually removingattributes from a tag management system may be difficult since theattributes may be linked with other attributes such as rules,transformations, etc. Thus, template or tag management objects may beuseful for organizing a tag management system, especially in the case ofnew configuration users where the learning curve to become proficient insetting up tag management configurations may be rather steep.Additionally or alternatively, if the tag management object to beremoved is a prerequisite for other tag management objects, then the tagmanagement system 140 may warn or require the user to remove thedependent tag management objects as well.

At block 214, the visitor processing system 142 or the tag managementsystem 140 may use the output configurations to analyze receivedinteraction data from a content site. As described herein, the visitorprocessing system 142 processes interaction data based on theconfigurations from the tag management system 140. Accordingly, datafrom end users may be tracked or analyzed using the instructionsspecified in the template objects. For example, the output of thetemplate implementation processes may include instructions sets toanalyze data that further conditionally generates output. The tagmanagement system 140 may present visualizations that are specified bythe template objects. Example visualizations are described in furtherdetail with reference to FIG. 28. Other example visualizations alsoinclude bar graphs such as the graphs depicted in FIG. 21. The analyzedinteraction data or the output of the template objects may generatepersonalized network page experiences, promotional network pages thatreflect the state of the user, targeted communications such as emails,or cross-computing device recognition data.

Turning to FIG. 3, an example tag management dependency process 300 isshown. The process 300 illustrates an example mode of operation of thecomputing environment 100 and may be implemented by the variouscomponents shown in the computing environment 100. For convenience, theprocess 300 is described in the context of the computing environment100, but may instead be implemented by other systems described herein orother computing systems not shown. The process 300 provides one exampleapproach by which tag management dependencies may be determined.Depending on the embodiment, the method 300 may include fewer oradditional blocks and/or the blocks may be performed in order differentthan is illustrated.

At block 302, the tag management system 140 accesses a first templateobject. Block 302 may be similar to block 202 of example method 200 ofFIG. 2. In some embodiments, the tag management dependency process 300may occur during at the end of an implementation process for a templateobject, such as after block 212 of FIG. 2. For example, the tagmanagement dependency process 300 may advantageously complete templateobjects that depend on a first template object, thereby increasing theefficiency of tag management configuration.

A block 304, the tag management system 140 determines whether the firsttemplate object is a prerequisite for other template objects. Block 304may be similar to block 204 of the example method 200 of FIG. 2 indetermining prerequisites. However, block 304 may differ from block 204in that, instead of determining whether a template object has anyprerequisites, the tag management system 140 determines whether thefirst template object is the parent or has any dependents that may alsobe completed or are near completion.

At block 306, the tag management system 140 accesses a second templateobject. The tag management system 140 accesses the second object thatwas determined to have the first object as a prerequisite. Block 302 maybe similar to block 202 of example method 200 of FIG. 2.

At block 308, the tag management system 140 determines whether thesecond object is ready to be implemented. For example, if the componentsof the second template object have been initialized, which may occur viathe completion of a first template object, then the tag managementsystem 140 may proceed towards implementing the second template objectat block 312. In some embodiments, a configuration user may be promptedvia a user interface to confirm whether to implement the second templateobject. Accordingly, block 312 may correspond to some of the blocks ofthe example method 200 of FIG. 2 such as blocks 210 or 212 forgenerating output or a tag management object. Otherwise, if a componentof the second template object, such as a template attribute, has anunassigned data value, the tag management system may proceed to block310. It will be appreciated that the tag management system 140 mayrecursively process the second template object once it has beenimplemented to see if there are further children templates that could beimplemented such as by returning to block 302.

At block 310, the tag management system 140 may prompt the user tocomplete the second template object. For example, if there arecomponents of the second template object that require user input, thenthe tag management system 140 may walk the user through theimplementation process for the second template object, which maycorrespond to the example method 200 of FIG. 2. Once the interviewprocess has been completed for the second template object, the tagmanagement system 140 proceeds to block 312 to implement the secondtemplate object. In some embodiments, the tag management system 140 mayidentify and present second template objects that are near completion tothe user. The presentation of second template objects may include anindication of the completion status of the second template objects suchas a percentage value (e.g., “90% complete”) or a visualization such asa progress bar.

Turning to FIG. 4, an example template distribution process 400 isshown. The process 400 illustrates an example mode of operation of thecomputing environment 100 and may be implemented by the variouscomponents shown in the computing environment 100. For convenience, theprocess 400 is described in the context of the computing environment100, but may instead be implemented by other systems described herein orother computing systems not shown. The process 400 provides one exampleapproach by which template objects or components may be distributed. Forexample, the tag management system 400 may include a templatemarketplace for configuration users to access template objects,components, or collections of template objects. Depending on theembodiment, the method 400 may include fewer or additional blocks and/orthe blocks may be performed in order different than is illustrated.

At block 401, the template distribution system 150 may receive a requestfor a template object, component, a collection of template objects, orsome combination thereof. For example, a configuration user may requesta collection of template object or a collection of template objects viathe tag management system 140. The tag management system 140 may requesta new version of a template object, component, or a collection oftemplate objects. Additionally or alternatively, the templatedistribution system 150 may push a new version of a template object,component, or a collection of template objects. In some embodiments, thetemplate distribution system 150 and the tag management system 140communicate via an Application Programming Interface (API).

At block 402, the template distribution system 150 accesses a firsttemplate object or a collection of template objects. The receivedrequest at block 401 may identify objects that the template distributionsystem 150 should access. Block 402 may be similar to block 202 ofexample method 200 of FIG. 2.

At blocks 404 and 406, the template distribution system 150 determineswhether the one or more template objects are ready to be distributed,should be deprecated or removed, or the requesting user or account hassufficient permissions to access the one or more objects. For example,the example objects depicted in FIGS. 29 through 32 include access rightproperties such as account, profile, or a published status. Examplepublish statuses include IN_PROGRESS, READY_FOR_PUBLISH, PUBLISHED,READY_FOR_UNPUBLISH, OUTDATED_IN_PROGRESS, OUTDATED_READY_FOR_PUBLISH,OUTDATED_PUBLISHED, or OUTDATED_READY_FOR_UNPUBLISH. If the one or moreobjects are not ready or the requesting account or user does not havesufficient permissions, then the template distribution system 150 mayprocess additional requests. For example, particular templates orcollections of templates may be accessible to particular users oraccounts such as being behind a pay wall.

At block 408, the template distribution system 150 determines relatedtemplate objects or related components. For example, as describedherein, a template object or its components may be assigned a versionsuch that newer versions of the template object or components may beaccessed. The template distribution system 150 may determine relatedcomponents or template objects using identifiers, as described herein.

At block 410, the template distribution system 150 distributes,deprecates, or removes the template object, components, or collectionsof template objects. For example, the template distribution system 150may determine that an underlying component of a template object may beoutdated, and the template distribution system 150 may transmit thenewer component to a respective tag management system 140 and instructthe tag management system 140 to deprecate or remove the oldercomponent. In some embodiments, when a component, or template object hasbeen updated, the configuration user may be notified and prompted tocomplete the updated template object. In some embodiments, the objectsmay be distributed over a network in a JavaScript Object Notation (JSON)data format.

IV. Example Tag Management User Interfaces

FIGS. 5 through 24 depict example tag management configuration-relateduser interfaces that can be output by the tag management system 140.These user interfaces include features for customizing visitor profiletemplate configurations, analyzing and generating segment reports,integrating visitor data collected by a visitor processing system withexternal vendor features, and the like. In particular, FIGS. 5 through20 depict visitor profile configuration user interfaces that can begenerated by the tag management system 140, FIG. 21 is an example userreporting interface described below, and FIG. 22 is an exampleintegration user interface which is also described below. In addition,FIG. 23 depicts an example data source user interface, and FIG. 24depicts an example data mapping user interface. Each of these userinterfaces are described in greater detail herein. Additionalinformation regarding visitor processing or the processing ofinteraction is described in further detail in the U.S. Pat. No.8,805,946, titled “SYSTEM AND METHOD FOR COMBINING CONTENT SITE VISITORPROFILES,” which was previously incorporated by reference herein in itsentirety, see, e.g., col. 4 ll. 10-col. 11 ll. 56 or col. 22 ll. 45-col.38 ll. 38. Generally, aspects of the tag management configurationdepicted in FIGS. 5 through 24 may be accomplished with the templatesdescribed herein. For example, any of the attributes depicted in FIGS. 5through 20 may be output by the template implementation processesdescribed herein.

FIGS. 25A through 28 depict example user interfaces for template-relatedfunctionality that can be output by the tag management system 140. Thefunctionality of the example template-related user interfaces mayautomate or overlap with some of the configurations or functionalitydepicted in FIGS. 5 through 24.

Each of the user interfaces shown includes one or more user interfacecontrols that can be selected by a configuration user, for example,using a browser or other application software. Thus, each of the userinterfaces shown may be output for presentation by a browser such as thebrowser 105 or the like or any other application software. The userinterface controls shown are merely illustrative examples and can bevaried in other embodiments. For instance, buttons, dropdown boxes,select boxes, text boxes, check boxes, slider controls, and other userinterface controls shown may be substituted with other types of userinterface controls that provide the same or similar functionality.Further, user interface controls may be combined or divided into othersets of user interface controls such that similar functionality or thesame functionality may be provided with very different looking userinterfaces. Moreover, each of the user interface controls may beselected by a user using one or more input options, such as a mouse,touch screen input, or keyboard input, among other user interface inputoptions.

Turning to the visitor profile configuration user interfaces of FIGS. 5through 20, a visitor profile configuration user interface 500 in FIG. 5is shown. The user interface 500 includes features for constructingvisitor profile templates, discovering data with respect to visitorprofiles created from visitor data by generating reports and featuresfor obtaining visitor profiles through API access. The example visitorprofile configuration user interfaces can provide functionality forconfiguration users to specify different types of visitor profiletemplates to be used in creating visitor profiles from captured visitordata.

In FIG. 5, the user interface 500 includes various menu options 510 foraccessing features of the visitor profile configuration module 242 andreporting module 248 of the visitor processing system 240. These menuoptions 510 include a set of tabs 512, 514 and 516 that may be selectedby a user. The menu options 510 include a build option 512 which uponselection can output a user interface 600 shown in FIG. 6 (describedbelow) or the like, a discover option 514 which upon selection canoutput a custom reports interface 2400 shown in FIG. 21 (describedbelow) or the like, and an API sampler option 516 which, upon selection,can output an integration user interface 2200 shown in FIG. 22(described below) or the like.

Using the build option 512, a configuration user can configure a visitorprofile. As described herein, a visitor profile can be made up of one ormore attributes (or rules, discussed below) which are defined orcustomized by a configuration user. Some attributes may be updated eachtime an event happens, such as a visitor interaction with a contentpage, while other attributors may be composed of multiple conditions andrely on values of other attributes created by the configuration user. Asdescribed above, badges are one example of these attributes. A badge maybe assigned to a visitor based on different attributes orcharacteristics of that visitor's interactions with the content page,whether within a single visit or over multiple visits.

One example of such a badge is shown in FIG. 5, the badge 530. The badge530 is shown as merely an example to illustrate one optionalconfiguration of an attribute that may be made by a configuration user.The badge 530 is titled “fan boy” and depicts a square icon with asmiley face superimposed therein. The “fanboy” badge represents thefollowing other attributes of a visitor, including that: the visitor hasviewed at least five products on the content site, has purchased atleast 90% of the products viewed, and has visited the content site atleast three separate times. These attributes may be configured by aconfiguration user using the various user interfaces shown in FIGS. 6through 20. Another example of a badge that might be configured by aconfiguration user is a window shopper badge. For instance, the windowshopper might be assigned to a user having the following attributes: theuser is visited at least four times to the content site, has never madea purchase, and has never added items to his shopping cart (or has addeditems to his or her shopping cart but has never purchased any of thoseitems).

As another example, a frequent visitor badge might be assigned to a userwho has visited a content site a total of at least 20 times and hasvisited at least two times in the last seven days. As another example,an impulse buyer badge might be assigned to a user who has an averageproduct view per purchase of less than two and a total productspurchased is greater than one. Further, still another example of a badgemight be a VIP user badge that might be assigned if a user has visited acontent site more than two times per week, has a spending total inexcess of $1,000, and has tweeted a link or liked an item on the contentpage on Facebook (or another social networking site). These badges andthe criteria that trigger their assignment to visitors are merelyexamples of a massively customizable number of badges that may beconfigured by configuration users to represent visitors to the contentsite based on the attributes of their visiting interactions with thecontent site.

As described above, data about the user visits may be obtained by thetag container and the tag on the tag server and provided to the visitorprocessing system. The visitor processing system can apply theattributes and rules for transforming those attributes into badges orother types of attributes which will be described in greater detailbelow. Further, using the reporting user interface 2100 of FIG. 21 orthe like, a configuration user can analyze different segments ofvisitors based on the data collected about those visitors andtransformed into specific attributes such as badges.

a. Attribute Creation Overview and Example Badge Attribute Creation

Turning to FIG. 6, a user interface 600 is shown that may be obtained bya user selecting the build menu option 512 from FIG. 5. In the userinterface 600, user interface 600 options for selecting attributes 612and rule 614 are provided. The attributes 612 can be attributes ofvisitors or attributes associated with visitor interactions with thecontent site. The attributes may be as simple as flags indicatingwhether a user has performed a certain interaction with respect to thecontent site, such as clicking on a link or purchasing a product.Conversely, the attributes may be as complex as a funnel representing apredefined ordered list of events, such as a payment funnel that occursthrough a series of clicks or item selection events made by a user.

In the depicted embodiment, the attributes option 612 is selected and aplurality of example attributes 620 are shown organized by title, type,and scope. Some examples of these attributes include a “visit startdate” that may be set to determine when a user started visiting awebsite, a “visit end date” that may be used to determine when a visitorended his visit, a “visit duration,” “lifetime visit count,” and thelike. The attributes 620 shown can be collected for all end users thatvisit the content site or a subset thereof. Options may be provided insome embodiments for a configuration user to determine which subset ofusers will be tracked according to the selected attributes.

The example types of attributes 620 shown include properties, metrics,dates, flags, sequences, and the like. Other attributes may also beprovided, examples of which will be described in greater detail below.The scope of the attributes can relate to the current visit that avisitor is experiencing with respect to the content site. The currentvisit can be a current browse session, for instance, with respect to thecontent site. The current visit may begin when the user initially loadsa content page from the content site and may end when the user leavesthe content page or is otherwise inactive for a period of time (such as30 minutes or more). Alternatively, the scope can refer to the visitorinstead of the current visit and may therefore correspond to lifetimevisits to the content page by the visitor. Other scopes are possible,including a configurable time period such as the past 30 days or thelike.

An add visitor attribute button 630 is also shown in the depictedembodiment. The add visitor attribute button 630 may be selected by auser to add a new visitor attribute to the list of attributes 620.Likewise, any of the attributes 620 may be selected by a configurationuser to edit the attribute 620. Upon selection of the visitor attributebutton 630, a user interface such as the user interface 700 of FIG. 7may be output for presentation to the user.

In the user interface 700 of FIG. 7, various options for selectingattribute types 710 to create a new attribute are shown. Upon selectionof one of the attribute types 710, the user can define specificcharacteristics associated with the attribute to be used for analysis ofdata collected with respect to end users. Users whose characteristics ininteracting with the content site satisfy characteristics or rulesassociated with an attribute can be assigned that attribute. In thedepicted embodiment, the attribute types that can be selected frominclude badges, which can include labels or other indicia used toidentify segments of users (e.g., frequent visitors); metrics, which canstore numerical data such as a return visit count; metric sets (ortallies), which can store sets or collections of metrics; properties (ortraits), which can store strings such as the name of a favorite product;property sets, which can store sets of properties; flags, which canstore true or false or Boolean values; dates, which can store a datevalue such as a date when a user last visited the content page; funnels,which can store a predetermined order list of events such as a paymentfunnel; and sequences, which can store an ordered list of events. Anadditional example attribute type (not depicted) includes a VisitorIdentifier, which can store a value that is used to identify a visitor.

For illustrative purposes, creation of an attribute of the badge type isshown in detail with respect to FIGS. 8A through 10. Example userinterfaces for customizing other attribute types are described belowwith respect to FIGS. 11 through 17.

Referring to FIG. 8A, if the badge attribute type 710 is selected inFIG. 7, a user interface 800 or the like may be output for presentationto a user. In the user interface 800, various options 802 forconfiguring a badge attribute are output for presentation to a user.These options 802 include controls 810 for configuring characteristicsof a badge, such as the title of the badge. In the depicted example, thetitle of the badge is “Window Shopper” and may have been entered by aconfiguration user. The options 802 also include controls 810 forentering any notes that a configuration user may wish to enter todescribe the badge.

In the depicted embodiment, the scope for badges is the visitor scope,and thus the badge may correspond to lifetime visits by the visitor.However, in other embodiments, the scope can be for a current visitinstead of the visitor scope, or for some other time period as describedabove. The user interface controls 810 also include functionality forspecifying further details about the badge itself, such as a text labelto be displayed for the badge, an image to be selected for the badge,shape, theme, and colors to be selected for the badge, and the like.Thus, a configuration user can define any characteristic to beassociated with a badge to distinguish the badge from other badges andto provide customization of the look and feel of the badge.

In addition, a created transformation button 820 is also provided thatcan be selected by a configuration user to add a transformation for thebadge. The transformation can include one or more conditions or rulesthat transform incoming visitor data collected by the visitor datacollector 244 into data that represents the attribute shown. Inparticular, in the depicted embodiment, the rules can transform visitordata into an indication of whether a visitor should be assigned the“Window Shopper” badge. The transformations may be performed by thevisitor data aggregator 246 of FIG. 2, which can aggregate the data andtransform the data into a useable format according to the one or moreconditions or rules specified in the transformation. By selecting afinish button 830, the badge attribute can be created.

If the created transformation button 820 is selected, a popup box (notshown) can provide options for either assigning a badge based on a setof conditions or removing a badge from visitors when those conditions nolonger apply. Other conditions for assigning the badge to the visitorcan include when the visitor is a new visitor or when it is a new visitor upon any page event or the like.

If a user selects to assign a badge from the popup box, a user interfacesuch as user interface 850 of FIG. 8B can be displayed. In the userinterface 850 of FIG. 8B, an example transformation 830 is shown. Theexample transformation 830 includes an example condition 932 thatassigns this badge to a visitor when a visit has ended. Additional rulesmay be specified for triggering the assignment of this badge byselecting an “attach a rule” button 834. Upon selection of the attachrule button 834, a list of rules 836 can be displayed, from which a usercan select to attach to the transformation. Some example rules are shownin the list of rules 836, including “visit is direct,” “visit isreferred,” and so forth. Other rules may be selected by scrolling downthrough the list 836. These rules may be created by accessing the rulesoption 614 of FIG. 6, for example, as described in greater detail withrespect to FIG. 18A below.

Rules can also be created by selecting an “add a new rule” button 838.Selection of this button 838 can cause a user interface 900 shown FIG. 9to be displayed. (A similar interface can be selected from FIG. 6 tocreate a new rule; see FIGS. 18A and 18B) In the user interface 900 ofFIG. 9, a new rule creation box is shown that includes options forcreating a new rule, including a text box 910 for titling the rule. Inthis particular embodiment for the window shopper badge, a user hascreated a title “Did not purchase this” for this rule. One or moreconditions 920 can be selected for the rule. The condition 920 shown isan “if” condition and includes subconditions 922, 924, 926, and 927. Thesubconditions include a dropdown box 922 for selecting an attribute (seealso FIG. 18B). Any attribute available in the attribute list 620 ofFIG. 6 can be selected or a new attribute can be created (see FIG. 18B).A dropdown box 924 includes options for comparing the attribute selectedin the box 922 with some value selected from box 926. The value selectedin box 926 can be an attribute, such as a metric, or some custom valuethat can be specified in box 927. Controls 928 are provided for adding(or removing) additional conditions to the “if” statement. An “add orcondition” button 929 may also be selected to add a Boolean “OR”condition to the rule.

Referring to FIG. 10, a user interface 1000 is shown in which an examplerule has been attached to the transformation 830 for the “WindowShopper” badge of FIG. 8B. The rule 1033 is entitled “visitor did notpurchase.” This rule is triggered if the data object “cart_value” isgreater than zero. This rule may have been created using the userinterface 900 of FIG. 9 to specify that the data object “cart_value,”selected from the dropdown box 922, is greater than (box 924) a customvalue (box 926) of zero (text entered into box 927).

Thus, in certain embodiments, the badge window shopper created in FIGS.8 through 10 can be assigned to a visitor when a visit has ended and ifthe visitor did not purchase as specified by the rule 1033. Of course,additional rules may also be attached to any badge attribute to create amore complex set of conditions or rules that would trigger the badgebeing assigned to a visitor. Likewise, similar sets of one or more rulesor conditions can be attached to a badge attribute to remove or deassigna badge from a visitor.

b. Example Attribute Creation—Other Attributes

FIGS. 11 through 17 illustrate example user interfaces for creatingother types of attributes. Referring specifically to FIG. 11, an exampleuser interface 1100 is shown for configuring a metric attribute. Asdescribed above, metric attributes can store numerical data about a uservisit or collection of visits. In addition, metrics can performoperations on numerical data to produce new metric values, for instanceby performing transformations, much like the transformations that werediscussed above with respect to the badge attribute. The user interfacecontrols for configuring the metric attribute are similar to the userinterface controls for configuring the badge attribute in some respectsincluding, for example, controls 1110 for creating a title and enteringoptional notes about the metric attribute. In addition, a scope selector1112 allows the scope to be identified for this metric attribute asbeing either associated with the visitor (e.g., over a collection of thevisitor's visits) or for the current visit that the visitor has with thecontent site. Attributes created with the “current visit” scope can betriggered within each individual visit, as opposed to over severalvisits in some embodiments.

A “create a transformation button” 1120 may be selected by the user tocreate transformations. Upon selection of this button 1120, a select box1130 is shown giving options for creating different types oftransformations to associate with this metric attribute. These types caninclude an increment or decrement metric that increments or decrements ametric based on a set of conditions. For instance, a visit count can bea metric that uses the increment transformation such that each time anend user visits a content site, this metric is incremented by one toproduce a total visit count over the lifetime of the visitor. Othermetric creation options in the select box 1130 include a set ratiometric or transformation that can set the quotient of two metrics as anew ratio metric; a set product transformation that can set the productof two metrics as a new metric; a set difference transformation that canset the difference of two metrics as a new metric; a set sumtransformation that can set the sum of two metrics as a new metric; setmetric transformation that can set the metric to a specific number; anda set difference between two dates transformation that can set thedifference between two dates as a new metric. These transformations areexamples and may be further combined, for example, by creating both aproduct and a sum, or both a quotient and a difference, or any number ofdifferent operations to create a single metric from a plurality of datainputs related to visitor data.

Although not shown, a similar user interface could be used to define ametric set. Metric sets can include a set of metrics that is dynamic innature, in contrast to metrics, which may be static in nature. Anexample of a static metric is “time on site,” which can represent theamount of time a user spent in a browse session on a content site. Ametric set can grow over time with name-value pairs that representchanging metrics with respect to user visit behavior. For example, ametric sent might include an array of times to be collected, such as“time-spent[“football”]=120 minutes, time-spent[“baseball”]=60 minutes,”etc. The values in a metric set may be determined at runtime, ratherthan during configuration, although the opposite may be true in someembodiments.

For instance, as shown in FIG. 12, an example user interface 1200depicts a transformation 1230 selected from the create a transformationbutton 1120 to set a ratio. In the depicted embodiment, the options 1230enable a metric to be set to a first attribute value 1232 selected froma dropdown box divided by a second attribute value 1234 selected from adropdown box, when a certain triggering event occurs selected from adropdown box 1236 (such as when the visitor is a new visitor or when thevisit ends, etc.). Likewise, a rule 1238 can be attached to the metricto apply further processing or configuration to the metric. Rulecreation using the attach a rule button 1238 can be similar to rulecreation described above and below with respect to FIGS. 18A through 20.

FIG. 13 depicts an example user interface 1300 for configuring aproperty attribute. The user interface 1300 is similar to the other userinterfaces described above for creating or configuring attributes. Forexample, the user interface 1300 includes options 1310 for adding atitle and optional notes to associate with the property attribute aswell as scope buttons 1312 to determine the scope of this attribute.Upon selection of a creative transformation button 1320, transformations1330 are shown. One or more transformations can be created for thisattribute similar to the other attributes described above. Thetransformation 1330 provides options to set a property to a custom valueor another value defined elsewhere in the visitor processing system. Forinstance, data sources can be specified that are provided in the contentsite's content pages (see, e.g., FIG. 23). These data sources caninclude, e.g., a user name of the visitor, page name, cart value for anelectronic shopping cart value, or any other piece of data which thecontent page wishes to define and track. The property attribute can beset to this particular value specified by a data source or any otherattribute via the transformation 1330. As a result, the propertyattribute can be stored and also operated upon by other attributes orrules. As an example, a “cart_value” property attribute can be checkedby a rule in a “Window Shopper” badge attribute to determine whether auser ever purchases items or is merely just looking. Likewise,properties may be used to filter segments or otherwise arrange resultsin a reporting user interface (see, e.g., FIG. 21).

Although not shown, property sets can be configured similarly. Theattribute of a property set can contain more than one assigned stringproperty value. If a property (not a property set) called “category” isset to “football” (e.g., representing a football-related link selectedby a user) and is then set again to “baseball” (e.g., representing asimilar link), the result may change from “category=football” to“category=baseball.” Each of these properties is a string. In contrast,as property set called “category” can be first set to “football,” withthe result that “category=[football],” and can then be set to“baseball,” with the result that the string “baseball” is appended tothe property set such that “category=[football, baseball].” Propertysets can be used to detect correlations in visitor data, such as whethera visitor selected links related to both football and baseball within avisit (or multiple visits) to a content page.

In FIG. 14, another example user interface 1400 is shown, which can beused to configure a flag attribute. The user interface 1400 alsoincludes options 1410 for assigning a title and optional notes to theattribute as well as a scope button set 1412 to define the scope of theattribute. A create a transformation button 1420 is also shown, whichcan allow one or more transformations to be created. An exampletransformation 1430 shown can allow the flag to be set to a Booleanvalue such as true or false when a triggering condition or conditionsoccur, as defined by the dropdown box 1434, and optionally when one ormore rules are satisfied as may be defined by attaching a rule 1436. Ina simple example, the flag attribute may be a new visitor attribute andmay be assigned when the condition of a new visitor being detectedoccurs. In another example, the flag attribute may be titled “added itemto cart” and may be triggered when the condition of a visitor adding anitem to a shopping cart has occurred. This condition may be detected bya rule that detects when their cart value associated with the visitor isgreater than zero.

Turning to FIG. 15, an example user interface 1500 is shown forconfiguring a date attribute. Options 510 are provided for specifyingthe title of the attribute and optional notes are shown as well as scopebuttons 1512 for selecting the scope of the attribute. A creative atransformation button 1520 is shown, which upon selection, enables theuser to select from an options popup box 1522 to either “capture thedate” to set the date to the current time stamp or to “set a date” basedon a set of conditions. In the “capture the date” transformation shownas example transformation 1530, the date attribute can capture the dateand time when one or more following conditions are met specified bycondition 1532, such as during a visit. A rule may also be attachedusing button 1534. Thus, the date and time may be captured, forinstance, when a user adds an item to a shopping cart or clicks acertain link taking the user to a certain page, etc.

In FIG. 16, an example user interface 1600 is shown for configuring afunnel attribute. Option 1610 for assigning the title and notes aresupplied in the depicted embodiment. Scope variables are not provided asthe funnel attribute can be determined for a single visit.Alternatively, funnels can be determined from multiple visits. Create astep button 1620 is provided similar to the creative transformationbuttons described above. A funnel may include a series of stepsincluding one or more steps that, once satisfied, indicate that theattribute has occurred for a particular visitor. For instance, a funnelattribute can represent a series of steps taken by a visitor prior to(and optionally including) a purchase. Such a purchase funnel can beindicative of how close visitors come to purchasing items; visitors whomake it further into the funnel come closer to purchasing, and viceversa.

One example step 1630 is shown to update the funnel, including options1632 through 1638 for defining when the step has occurred. For instance,a text box 1632 is provided for specifying a title of the step, and aselect box 1634 and attribute button 1636 are provided for addingattributes to capture related to the funnel. A condition box 1638 isprovided for determining when this step is considered to have occurred.Further, a rule may be attached by selecting a rule button 1640.

In certain embodiments, funnels can provide for the configuration of anexpected flow that has a known (or anticipated) start and end. Forexample, a shopping experience on an electronic commerce website can bemodeled as a funnel attribute, with step 1 being viewing a product(e.g., any number of times), step 2 being adding the item to a cart,step 3 being to proceed to checkout, step 4 being filling out shippinginformation, step 5 including filling out billing information, and step6 including confirming the order. The funnel attribute can allow thevisitor to be traced through the funnel, providing a resulting report ofwhere visitors fall out of the funnel (e.g., by stopping at a certainstep in the funnel). This report may be useful to configuration userswho wish to determine the conversion rate of end users, among otheruseful data.

Funnel attributes may be time-ordered, such that in order for a funnelto be associated with a visitor, the visitor must follow the steps ofthe funnel in order. Other configurations that are not based ontime-ordering are possible. Data may be captured at each step of thefunnel or at the end of the funnel. For instance, it may be useful toinspect the value of a shopping cart that a user abandoned midway into apurchase funnel. Other funnel attribute features can include the abilityto make a step optional, meaning it can be skipped. In the exampleabove, shipping is often skipped because the billing info often providesall the info needed for shipping.

Purchase funnels are merely one example use of funnel attributes. Otherexample uses for funnels include campaigns, flight check-ins, emailsign-ups, or any other sequence of steps that use an online tool on thecontent site.

Referring to FIG. 17, an example user interface 1700 is shown forconfiguring a sequence attribute. The user interface 1700 includesoption 1710 for specifying a title and optional notes and a scope button1712 for selecting the scope. In addition, the user interface 1700includes a button 1720 for creating an entry, which can be similar tothe create transformation buttons described above. One or more entriesmay be created to update a sequence. An example entry 1730 is shown thatrecords an event for the sequence. The entry 1730 can capture attributedata specified using a select box 1732 and add/or attribute button 1734upon a condition occurring as specified by the dropdown box 1736.Optionally, a rule may also be attached 1738.

In contrast to funnel attributes, which may have a defined end-goal(such as a purchase), sequences can log or track more general datapoints, such as click actions or link selection actions of an end user.Sequences can provide a mechanism for logging significant visitor eventsas a historical trace, without the need to store all the data betweenthe events. For example, an end user's purchase history with respect toan electronic commerce site can be represented by a sequence attribute.The purchase history sequence can include a list of the user's purchasesbut may not include, for example, each of the user links selectedbetween purchases. Another example of a sequence can be a search keywordhistory that resulted in a user finding a content page. Yet anotherexample can include a list of movies watched (e.g., in a Netflix™queue), and the like. Events in a sequence may be associated with atimestamp so that later analysis of the sequence can compare timestampsof the events.

c. Additional Rule Creation Features

FIG. 18A shows another view of the example user interface 600 of FIG. 6.In particular, the user interface 1800 shows that the rules option 614of FIG. 6 is selected. A set of rules 1804 is shown, which may have beencreated by the user or provided by the vendor of the visitor processingsystem. Each of the rules 1804 may be selected for customization by aconfiguration user. A new rule may also be created by selecting the addrule button 1806. Various features for creating rules have beendescribed above.

In addition, selecting the add rule button 1806 can show a userinterface, such as an example user interface 1850 shown in FIG. 18B. Theuser interface 1850 provides options 1810 for titling and annotating arule as well as conditions 1830 to specify for the rule. Selection ofthese conditions can include dropdown boxes 1832, 1834, and 1836 forspecifying subconditions associated with the condition. An example listof attributes 1833 is shown, from which visitor attributes may beselected, data sources may be selected, or the like. Mathematicaloperators may be selected via the dropdown box 1834 to compare theattribute with a custom value as specified in the dropdown box 1836 ortext box 1838. For example, an attribute may be selected from thedropdown box 1832 and compared with a metric or property that is definedelsewhere in the set of attributes described above. Select boxes 1840can be used to add or take away conditions. An “add or condition” button1842 can be selected to add one or more additional Boolean “OR”conditions.

FIG. 19 shows an example user interface 1900 similar to that of FIG.18B, depicting the custom value dropdown box 1836 selected to showvarious custom values 1837 that could be specified when creating a rule.In FIG. 20, an example user interface 2000 shows how attributes can beadded from within the rule creation process with various attributestypes 2010 being selectable. The user interface 2000 may be output forpresentation to a user upon selection of an add visitor attribute button1839 in FIG. 19 and may have similar functionality to the attributioncreation user interfaces described above.

d. Example Report Generation Features

Turning to FIG. 21, an example reporting user interface is shown. In theexample reporting user interface 2100, options are shown for filteringthe various attributes that have been defined for visitors to produce aset of results 2140 that illustrate aggregations or segments of visitorprofile data. The filters include metrics filters 2112 that enable aconfiguration user to select different metrics associated with visitorsas well as flag 2114 and badge filters 2116. Other filters may also beincluded in other embodiments.

A user may select one or more of the metrics filters 2112 to adjustmetrics associated with different users to be output in the reportingsection 2140. In the depicted embodiment, these metrics include productspurchased, orders placed, total visits, language, total purchase count,total purchase amount, and time of sale. These metrics may have beendefined using the interfaces described above. Different slider selectiontools 2111, 2113, and 2115 allow users to adjust the values of metricsdata to be displayed. For instance, the slider 2111 depicts values for atotal purchase count that may be selected. In this depicted embodiment,the user selected a total purchase count between 10 and 30 to therebyview a segment of visitors that purchased between 10 and 30 items.Likewise, the slider 2113 has been used to select a total purchaseamount between values of 30,000 and 60,000. The slider 2115 shows themetric “time of sale” being selected between 10:00 a.m. and 5:00 p.m.

Within the flag filters 2114, various flags are shown such as “has madepurchase,” “emailed link,” “retweeted link,” and “returning visitor,” aswell as a number of times that those flags have occurred indicated byamount 2119. Check boxes 2117 next to the flags are provided forselectively selecting the flags to filter the output of the reportingarea 2140. Similarly, check boxes 2117 are next to different badges inthe badge filters 2116. Different badges are shown such as “VIP,”“window shopper,” “fan boy,” and the like, next to amounts 2119 ofvisitors that have earned these badges or been assigned these badges.Any combination of the badges may be selected with the check boxes 2117to filter the output of the reporting display 2140.

The output of the reporting display 2140 can also be adjusted byselecting the different perspective to show the reporting data fromusing a drop down box 2120 that shows (in this embodiment) that theperspective is from the point of view of flags. Thus, different bars2141 in the reporting display 2140 reflect value amounts 2119 thatdifferent flags represent, such as “has made purchase,” “emailed link,”etc. A query is shown at the top represented by controls 2136 thatrepresents the selections of the filters 2110 to filter the differentflags. Each of the subaspects of the query can be deselected by clickingon X buttons 2137. In addition, selection of a particular bar of the bargraph 2142 can show snapshots 2150 of the metrics. The example reportinginterface 2100 is illustrative only and may be varied considerably inother embodiments.

e. Example API Data Integration Features

Turning to FIG. 22, an example user interface 2200 is shown forintegrating raw data output by the visitor processing system with thirdparty vendor data or systems. The integration user interface 2200 canprovide functionality for building a sample query using controls 2210 toquery their live feed or other date ranges for data. Additional APIaccess can be provided for developers of third party vendors to accessthe raw visitor data collected by the visitor processing system andprocessed using the transformations and rules described above.

The raw data may be used for more than just reporting, either by thevisitor processing system itself or these third party vendors. Forinstance, the data output by the visitor processing system can be usedfor generating ads or ad campaigns, email campaigns, personalizationincluding ads or recommendations or the like. For instance, in oneembodiment the visitor processing system outputs a periodic feed (forexample daily, monthly, weekly, hourly) of data from the visitorprocessing system to external vendors so that the vendors can use thisdata to update information about visitors. The data in the feed can beused to perform business intelligence, aggregate the data for long-termtrends and trend analysis, and the like.

In yet another embodiment, the raw data or processed data output by thevisitor processing system can be used to update the content site itselfby personalizing the content of the content site based on the visitorsand their attributes. For instance, a configuration user may create a“chatter” badge that is assigned to visitors who are influenced by chatbecause they tend to purchase items when they are using a chat functionon the content site. If such a visitor comes to the content site, thecontent site can programmatically personalize itself to show a chatwindow more prominently for that particular visitor. As another example,if a visitor is assigned a VIP badge, the content site may not show adsto the user. If the user is a regular buyer, the content site may give a10% discount offer to that user. As yet another example, if a badge“early adopter” is assigned to a visitor, the content site may show thelatest electronic gadgets to the user or prioritize those gadgets in adisplay to a user over other gadgets or products.

f. Example Data Source Specification and Mapping Features

Referring to FIG. 23, an example data source user interface 2300 isshown. As described above, data sources may be accessed when creatingattributes and/or rules to access data that is part of the content pageor that is associated with the browser or end user system itself. Thesedata sources may be specified by a configuration user associated withthe content site so that the visitor processing system can be aware ofthese data sources and know to collect their data. For instance, if thecontent site is an electronic shopping site and has a shopping cart, andif one of its content pages has a “cart value” data source, theconfiguration user can use this user interface 2300 to specify that thecart value data source is available and should be obtained for analysisin the visitor data.

A button 2302 is provided for adding a data source. Upon selection ofthis button, a row can be added to the user interface 2300. Datainserted in the new row can be saved in computer storage, such as in adatabase. The row can include a text box 2310 for specifying the name ofthe data source, select boxes 2320 for specifying the type of the datasource, and a description box 2334 providing a written description ofthe data source. The name 2310 in the text box 2310 can be the name ofthe data source used by the content site. Specifying this name canenable the visitor processing system to be aware of which variable ordata source to look for when obtaining data using the tag container 114and/or tag 118 (see FIG. 1).

The type of the data source identified in the dropdown box 2310 can be adata object that is associated with the page itself, it may be aJavaScript page variable or other script value associated with the page,a meta tag associated with the page, a query string parameter associatedwith an HTTP PUT or GET statement, or a cookie value that is associatedwith the end user system or browser. Other options are also possible.Thus, if the data sources are specified in the user interface 2300, thevisitor processing system can obtain data from the specified datasources using an appropriate tag 118.

As shown in FIG. 24, a user interface 2400 for mapping the data sourcescan be used for some tags. The user interface 2400 shows example tagsadded to the tag server(s) 120 from third party vendors. In the depictedembodiment, these tags include a live person tag and a Google™ Analyticstag. Configuration details 2702 for the Google™ Analytics tag areprovided and mapped data sources 2710 are also shown. The mapped datasource functionality can be provided to enable a user to map the datasources defined in the user interface 2300 to a data source in the tagvendor's tag. However, in certain embodiments, such mapping is notperformed by the visitor processing system for the visitor attributesand rules described above. Rather, the mapping may not be needed becausethe visitor processing system can collect all the data sources specifiedby the configuration user and can make these available in the attributesand rules configuration displays without further mapping required.Mapping may instead be used with such visitor rules and attributes inother embodiments.

g. Example Tag Management Template User Interfaces

FIGS. 25A through 25I depict example user interfaces corresponding to atemplate implementation process that can be output by the tag managementsystem 140. In FIG. 25A, the example user interface 2500 includes atemplate selection area 2502. As depicted, the template selection area2502 includes a “Starter Pack—Base” template element 2598 that may beselected by a configuration user. The “Starter Pack—Base” templateelement 2598 may correspond to a template object, as described herein.The example starter template object may be configured to walk aconfiguration user through identifying back end configurations toconfigure their content site to track interaction data with the site. Anadvantage of the example starter pack, is that implementation of thestarter template object may be configured to complete or to nearlycomplete other template objects, which thereby may reduce theconfiguration time for the content site. In FIG. 25B, once aconfiguration user has selected to implement the template, the user maybe presented with an introduction user interface that indicates inputsor outputs of the template.

FIGS. 25C through 25G depict example prompts and elements of thetemplate user interfaces. In FIG. 25C, the example user interface 2500includes one or more prompts and one or more corresponding inputelements. Generally, the example user interface 2500 of FIG. 25C mayprompt the configuration user to identify particular parameters of auniform resource identifier. For example, the prompts 2503A and 2503Brequest a configuration user to select a value for the page nameattribute. In the example, a default page name option 2504 has alreadybeen prepopulated; however, a configuration user may select an alternateoption via the dropdown element. The prepopulated value may be based ona pre-existing attribute, such as a pre-existing attribute that wascreated by another template implementation process or that was createdindividually by a configuration user. In some embodiments, prompts oruser input elements that have an existing value may be suppressed in theuser interface. For example, the tag management system 140 may determinea subset of user interface elements to present to the user based onpre-existing components of the template object already being completedor having a value. The tag management system 140 may use the user inputsuch as variable mappings for the template object to generate output, asdescribed herein. In FIG. 25D, the example user interface 2500 includesadditional one or more prompts and one or more corresponding inputelements. For example, the example user interface 2500 of FIG. 25Dincludes a prompt requesting user input for the page type of the homepage for the content site and a corresponding text input element 2505.Example user input for element 2505 is the input value “home,” which maybe a textual string. Accordingly, the tag management system 140 may usethe user input to generate interaction data associated with uniformresource identifiers (e.g., a uniform resource locator or URL) with thetext “?page_type=home”, for example. FIGS. 25E through 25G depictsadditional one or more prompts and one or more input elementscorresponding to example attributes such as end user related informationand content site event-related information.

For example, in FIG. 25G, the depicted prompts and input elements relateto content site event-related information. Example content site eventsthat can be identified by the corresponding user input include, but arenot limited to, email signup, link selection, user login, user logout,user registration, user updates, file downloads, or playback of mediacontent. As described herein, the input elements may correspond toportions of uniform resource identifiers including attribute pair valuessuch as “?event=userlogout”, “?event=userlogin”, or“?action=registration,” for example. Additionally or alternatively, theinput elements may correspond to other methods of tracking in userinteractions such as detecting one or more keywords or phrases in acontent page or Document Object Model.

FIGS. 25H and 25I depict example prompts and elements to completeimplementation of a template object. In FIG. 25H, the example userinterface 2500 includes a naming input element 2506 for a configurationuser to name their tag management object that will be generated from thecorresponding template. In FIG. 25I, the example user interface 2500provides a summary of the input values that the configuration user hasspecified through the template process and includes a complete element2508 for the configuration user to select when ready to complete theimplementation of the template object.

FIGS. 26A through 26C depict example user interfaces that may beavailable upon implementation of one or more template objects. In FIG.26A, the example user interface 2600 includes an attribute summary area2602. The example attribute summary area 2602 may presentrepresentations of configured attributes for a particular content site.As depicted, there may be many configured attributes for a content sitesuch as hundreds of different attributes (or more) for tracking orprocessing interaction data. Example attributes that can be configuredfrom the completion of one or more template objects include determiningthe end user's browser type, the end user's browser version, the enduser's computing device, the end user's operating system, the end user'saverage visit duration in minutes, the end user's average number ofvisits per week, view counts of particular content site pages, orvarious other end user information or categorizations, such as being afirst visitor or a frequent visitor.

In FIG. 26B, user selection of the template filter element 2604 maycause the attribute summary area 2602 to present attributes that weregenerated according to a template process such as the example processdepicted by FIGS. 25A through 25I. Accordingly, the example templateprocess, such as the Starter Pack template process, may generatenumerous attributes. Example attributes that may be outputted bytemplate process include metrics or tallies for one or more visitorssuch as a view count of a category page, total page views, confirmationevents, or days since a last visit; traits such as end user preferences(e.g., favorite page category) or end user information—customer city,email address, social media identifiers, user name, identificationnumber, phone number, postal code; flags or events such as logging in,completing an order, converting, registering; date information such as adate or timestamp or last login, visit, or registration. In someembodiments, a configuration user may select an attribute representationwithin the attribute summary area 2602 to view more information about aparticular attribute.

In FIG. 26C, the example user interface 2600 depicts an exampleattribute that was the output of a template process. For example, theattribute representation 2606 may be selected within the attributesummary area 2602 to present the attribute detail area 2608. As depictedby the attribute detail area 2608, one attribute (of many that may begenerated by a template process) may include instructions fordetermining summary data from interaction data. The example attributeinstructions of within the attribute detail area 2608 indicate a productmay be determined to be purchased if the page title, in a content pageor Document Object Model, contains the text “purchase.” Accordingly, thetag management system 140 may efficiently generate the attribute for auser that completes the template process without having to understand orconstruct the underlying instructions of various tag managementconfigurations.

FIGS. 27A through 27M depict example user interfaces corresponding toanother template implementation process that can be output by the tagmanagement system 140. Aspects of the example user interface 2700 maycorrespond to a first template process that is a prerequisite to asecond template process. In FIG. 27A, the example user interface 2700includes a template selection area 2702. Elements of the example userinterface 2700 of FIG. 27A may be similar to elements of the userinterface 2500 of FIG. 25A. As depicted, the template selection area2702 includes a “Window Shopper” template element that may be selectedby a configuration user. Other example templates that may be selectedthrough the template selection area 2702 include: “Identify ActiveShopper,” “Set up Back End Data Layer,” and “Category Affinity” (notillustrated).

In FIG. 27B, the example user interface 2700 includes a notificationarea 2704 indicating that the “Set up Back End Data Layer” template is aprerequisite to completing the “Window Shopper” template. Accordingly,user selection of the next element 2706 causes the example userinterface 2700 to progress through the “Set up Back End Data Layer”template seamlessly before permitting the user to complete the “WindowShopper” template.

FIGS. 27C and 27F depict additional example prompts and elements of atemplate user interface. In FIG. 27C, the example user interface 2700includes one or more prompts and one or more corresponding inputelements, which may be similar to the example user interface 2500 ofFIGS. 25C through 25G. However, in contrast to the examples userinterface 2500 of FIG. 25C, which had default options preselected,example user interface 2700 may not have preselected input options.Accordingly, in FIG. 27D, a user may select an option from the optionselector 2708. Again, similar to the mappings specified in the exampleuser interface 2500 of FIGS. 25C through 25G, the user inputcorresponding to the example user interface 2700 may specify the contentsite mappings to implement one or more templates. In this case, toimplement the “Set up Back End Data Layer” template, the prompts of theuser interface 2700 request user input corresponding to a productidentifier, a product category, an order identifier, an order total, andan order customer identifier, that may be inputs to the template processfor generating the outputs of the “Set up Back End Data Layer” or“Window Shopper” templates, as described herein. As described herein,the configuration details that a user may specify within the inputelements of FIGS. 27C and 27D may correspond to portions of uniformresource identifiers, content pages, or a document object model fordetecting end user interactions.

FIGS. 27E and 27F depict example prompts and elements to completeimplementation of another template object, which may be similar to theelements of the example user interfaces 2500 of FIGS. 25H and 25I.

FIGS. 27G and 27M depict additional prompts and elements of a templateuser interface that may be presented following completion of aprerequisite template user interface. In FIG. 27G, the example userinterface 2700 indicates that the “Set up Back End Data Layer” templateprocess has been completed and user interfaces corresponding to the“Window Shopper” template will be presented. In FIG. 2711, the exampleuser 2700 includes an attribute selector 2710 where the options forselection include options 2712A and 2712B. As depicted in FIG. 27I, theproduct page visited option 2712B has been selected instead of the quickview event 2712A. The options corresponding to element 2710 relate tothe determination of when a visitor has viewed a product within thecontent site. For example, determination of a product page visit by thetag management system 140 may be based on the processing of interactiondata indicating that a specific “product page” has been requested byuser, in the alternative, a determination based on a quick view eventmay include a user expanding a product in a product page with multipleitems.

In FIG. 27J, the example user 2700 includes a prompt for theconfiguration user to select a badge attribute to assign to a visitorand a corresponding user input element 2714. For example, in oneembodiment, the tag management system 140 may generate an outputattribute, such as the window shopper badge example here, which may beautomatically assigned to end users of a content site when theconditions specified by the template object are satisfied.

FIGS. 27K and 27L depict example prompts and elements to completeimplementation of another template object, which may be similar to theelements of the example user interfaces 2500 of FIGS. 25H and 25I. InFIG. 27M, example user interface 2700 includes an example notificationarea 2716 that indicates the configuration user has completed thetemplate implementation process. The template user interfaces describedherein may include a similar notification or completion page to the userinterface 2700 of FIG. 27M.

FIG. 28 depicts an example user interface to display implementedtemplates or tag management objects. The example user interface 2800includes a template display area 2820. As illustrated, the templatedisplay area 2820 may include user interface controls for viewing,editing, or deleting an implemented template. The template display area2820 may also include one or more visualizations that are automaticallygenerated by completing a template process. For example, completion ofthe template process depicted in FIGS. 27A through 27M corresponding toa window shopper template may generate the visualization for viewingwindow shopper badge counts for a time period such as the most recentrolling month. As described herein, the template object may includeinstructions for generating one or more relevant visualizationscorresponding to the output of a template object thereby reducing theconfiguration time of the tag management system or saving configurationtime or effort by configuration users. Example visualizations alsoinclude bar graphs such as the graphs depicted in FIG. 21.

V. Example Tag Management Template Data Model

FIGS. 29 through 32 depict example template objects or templatecomponents that may be used by the tag management system 140. Thetemplate object 2900A-2900B of FIG. 29, the template attribute 3000 andthe template operator 3050 of FIG. 30, the template rule 3100 and thetransformation template 3150 of FIG. 31, or the template audience 3200and the template collection 3250 of FIG. 32 may be in the same dataformat. The template attribute 3000 and the template operator 3050 ofFIG. 30, the template rule 3100 and the transformation template 3150 ofFIG. 31, or the template audience 3200 may be components of a templateobject, as described herein. An example data format is a JavaScriptObject Notation (JSON) data format. The example template objects ortemplate components may be stored in the template data source 162. Asdescribed herein, the tag management system 140 may use the templateobjects or template components to present the template user interfacesto implement the templates and to further configure the tag managementsystem 140. The example template objects or template components areillustrative and may not be executable or implementable in the formatshown.

In FIG. 29, the example template object 2900A-2900B includesproperty-value pairs that can define a template user interface. Forexample, the example template object 2900A-2900B includes a templateidentifier 2902, an array of one or more prerequisite templates, acorresponding account or profile, a name, a description, an associatedgraphic or color, or any other customizable properties, which mayconfigure the presentation of template user interfaces in the tagmanagement system 140, such as any of the example user interfaces FIGS.25A through 27M.

The example template object 2900A-2900B includes inputs 2912 and outputs2914. The prompts of the example template object 2900A-2900B maygenerate mappings between the inputs 2912 and the outputs 2914. Forexample, the prompt 2916 includes text configured to be display to aconfiguration user and a body property 2918. The example body property2918 may have the value “%% attributes.event_name %% contains %%%attributes.334fa162-5f85-45aa-a450-688e809eb8cf%%%,” which maycorrespond to a custom template syntax. In some embodiments, the customtemplate syntax specifies that read-only variables may be indicated by aspecial character such as “%%” and editable variables may be specifiedby another special character such as “%%%”. In other embodiments, thespecial character such as “%%” may correspond to an editable value, butthat may be editable with a warning. Accordingly, the value of theexample body property 2918 configures a template user interface topresent the read only attribute event name (an input) and theconfiguration user is prompted to select user input for the attribute“334fa162-5f85-45aa-a450-688e809eb8cf”. Thus, the example body property2918 may correspond to a user interface 2500 that includes an exampleinput element 2505 of FIG. 25D. As described herein, identifiers oftemplate objects or components may reference respective template objectsor components that may be defined in separate objects. The exampletemplate object 2900A-2900B includes version and revision property-valuepairs 2922 and a publish status 2924 for distribution to different tagmanagement systems. Example status values for the publish status 2924includes IN_PROGRESS, READY_FOR_PUBLISH, PUBLISHED, READY_FOR_UNPUBLISH,OUTDATED_IN_PROGRESS, OUTDATED_READY_FOR_PUBLISH, OUTDATED_PUBLISHED, orOUTDATED_READY_FOR_UNPUBLISH.

Example identifiers of template objects or components may include astring or Globally Unique Identifier (“GUID”). The strings“334fa162-5f85-45aa-a450-688e809eb8cf” or “event_name” are examples ofvalid identifiers. In some embodiments, identifiers may not beguaranteed to be unique, however, the chances of a repeating uniqueidentifier may be extremely low and/or negligible due to theirimplementation. For example, a unique identifier may be generated fromrandom or pseudorandom numbers with 122 random bits such that the totalnumber of unique identifiers is 2¹²². Thus, the unique identifiers areso large that the probability of the same number being generatedrandomly and/or pseudo-randomly twice is negligible. In someembodiments, shorter and/or longer identifiers may be used.

The tag management system 140 may determine prerequisites for templates.For example, the template object 2900A-2900B (“Identify OutdoorShopper”) includes the input 2912 that specifies an attribute input of“event_name”. The event_name attribute may be output of anothertemplate, “Set up Back End Data Layer,” for example. Thus, the “Set upBack End Data Layer” template may be a prerequisite for the “IdentifyOutdoor Shopper”. Accordingly, the tag management system 140 maydetermine prerequisites of template objects, or prerequisites ofprerequisites, etc., using the identifiers. Additionally oralternatively, the template object 2900A-2900B may include aprerequisites property-value pair attribute 2904, which may optionallyexplicitly identify prerequisite templates. The example prerequisitesattribute 2904 is a list or array containing identifiers identifyingother template objects. In some embodiments, the prerequisites attribute2904 may be for convenience of walking a configuration user through awork flow. In other embodiments, a process for determining prerequisitesmay rely on the prerequisites attribute 2904 instead of usingidentifiers for individual template components. Generally, aspects oftemplate objects may facilitate efficient configuration tag managementsystems. For example, a first template object may be curated by anadministrator or analyst to identify the base configurations foradditional second template objects such that the first template objectis a prerequisite for the second template objects.

In FIG. 30, the example template attribute 3000 includes property-valuepairs that can define an attribute. The example template attribute 3000is a VIP badge, which may be input or output of a template object. Forexample, the template object may include instructions configured toassign end users to the VIP badge attribute 3000. The example templateoperator 3050 includes property-value pairs that can define an operatorthat may be used by a template object. Example operator functionsinclude exists, contains, equals, equals ignore case, or contains ignorecase, or between.

In FIG. 31, the example template rule 3100 includes property-value pairsthat can define a rule; the example transformation template 3150includes property-value pairs that can define a transformation. Theexample template rule 3100 or the example transformation template 3150can include sets of instructions. The example transformation template3150 includes an identifier, which may correspond to the value of thetransformation identifier 2906 of the template object 2900A-2900B. Thus,the transformation may be configured by implementation of the templateobject 2900A-2900B. For example, the transformation sets the targetattribute (53ab5740-3482-4b74-b907-ad59949e5df6) to the value attribute(24550880-7568-4172-84d8-e7ce9014b930), both of which may be componentsof the template object 2900A-2900B.

The transformation template 3150 includes one or more rule identifiersthat refer to one or more rules. When the one or more rules aresatisfied the transformation template 3150 may be configured to cause atransformation via instruction sets. In this example, the transformationtemplate 3150 is configured to set an end user trait to complete_visitwhen one or more conditions of the sets of instructions are satisfied.The example transformation template 3150 refers to the template rule3100 (identifier fd2f3db8-2e58-4b11-b025-ca892ec19275). Thetransformation template 3150 includes the conditions component 3102 thatspecifies an operator such as “contains”. The “contains” operator may bea known operation of the tag management system 140. Alternatively, thevalue of an operator may be an identifier, such as the identifier“a63e2e86-eb9b-4471-ba46-e2353efa4e12” of the example template operator3050 of FIG. 30. Accordingly, template operators may be customized.Continuing with the example, the conditions component 3102 specifies aninstruction set to apply the operator (contains) to first and secondoperands (again, which may be components of the template object2900A-2900B). The instruction set may determine whether the firstoperand (event_name) contains the value of the attribute(334fa162-5f85-45aa-a450-688e809eb8cf) that was specified by the usercompleting the template process. For example, where event_name contains“log_out” (which is the value specified by the configuration user) theinstruction set may return true, which may then trigger the rulecorresponding to template rule 3150 to set the shopper trait tocomplete_visit. In some embodiments, example instruction sets mayinclude one or more operands. An example instruction set for three ormore operands include a “between” operation that may check for a firstvariable being between second and third operands. Other exampleinstructions sets include complex logic such as ((A==B) OR (C==D)) AND(E contains I)). An example instruction set for one operand includes anoperation for the “exists” operator.

Another example instruction set includes frequent home page visitorlogic. For example, the home page configuration, which indicates when auser accesses the particular home page of a content site, can be used byadditional template objects that include instruction set logic. Theinstruction set logic can use, for example, the “exists” operator toidentify instances of home page visits by a user from the home pageconfiguration that serves as the basis for determining a frequent homepage visitor badge. For example, the frequent home page visitor logiccan assign the frequent home page visitor badge when the number of homepage visits for a particular users exceeds a threshold. In someembodiments, the frequent home page visitor logic further uses a timeperiod, such as number of visits within a one month, two month, or oneyear time period.

In FIG. 32, the example template audience 3200 includes property-valuepairs that can define an audience. An audience may be a collection ofend user or visitor attributes. The tag management system 140 may takeactions on the audience to track end users or perform data analytics onthose end users, as described herein.

The example template collection summary 3250 may specify a collection ofcomponents or templates. The template collection summary 3250 may beused by the tag management system 140 for presentation of groups oftemplates to configuration users. In some embodiments, a templatecollection may be a logical grouping of related templates such astemplates for configuring back end data or identifying variousrelated-attributes of end users. As used herein, a collection oftemplates may also be referred to as a “playbook.”

VI. Example Implementation Mechanisms

FIG. 33 illustrates a computer system 3300 usable to implement one ormore of the systems (for instance, the end user system 102, the tagmanagement user system 104, analytics system 130, or the tag managementsystem 140) or servers (for instance, the site server 110 or tag server120) within the computing environment 100 of FIG. 1.

As shown in FIG. 33, system 3300 can include (i) one or more hardwareprocessors (CPUs) 3310, (ii) an input/output device(s) 3320 configuredto allow users to input and output information and interact with thesystem 3300 as well as transfer and receive data, (iii) one or more readonly memory (ROMs) devices 3330 or equivalents to provide nonvolatilestorage of data or programs, (iv) one or more displays 3350 such as acomputer monitor or other display device, (v) one more networkconnections 3340 and associated network interfaces 3342 configured toallow the system 3300 to connect to other systems, servers or portabledevices, as well as one or more memory spaces 3360 and one or moredatabases 3390. Database(s) 3390 may be further divided or distributedas one or more sub-databases 3390 a-3390 n, with the sub-databasesstoring feature or function specific information associated with aparticular feature or function. The various components shown in FIG. 33may be incorporated in one or more physical servers 3370. It is notedthat the various components shown in FIG. 33, including database 3390,are typically included as part of server(s) 3370, however, they may beexternal to server(s) 3370 in some embodiments. For example, database(s)3390 may be external to server(s) 3370 and may be part of a separatedatabase server system or networked database system. In some instances,the system may not be a server but rather a computing device like adesktop computer or mobile device.

One or more memory spaces 3360 may comprise DRAM, SRAM, FLASH, hard diskdrives or other memory storage devices, such as media drives 3380,configured to store operating systems 3362, application programs or data3364, and one or more memory spaces 3360 may be shared with, distributedwith or overlap with the memory storage capacity of database 3390. Insome embodiments, one or more memory spaces 3360 may include database3390 or in some embodiments database 3390 may include data 3368 as shownin memory space 3360. Data stored in memory space 3360 or database 3390may include information, such as tag management system information orother types of data described herein.

VII. Additional Embodiments and Terminology

Many other variations than those described herein will be apparent fromthis disclosure. For example, depending on the embodiment, certain acts,events, or functions of any of the algorithms described herein can beperformed in a different sequence, can be added, merged, or left outaltogether (e.g., not all described acts or events are necessary for thepractice of the algorithms). Moreover, in certain embodiments, acts orevents can be performed concurrently, e.g., through multi-threadedprocessing, interrupt processing, or multiple processors or processorcores or on other parallel architectures, rather than sequentially. Inaddition, different tasks or processes can be performed by differentmachines or computing systems that can function together.

In some embodiments, one or more parts of or all of the analytics system130 or tag sever 120 can be implemented in a distributed cloud platformthat provides redundant or geographically dispersed access. Although notillustrated herein, one such example implementation is described andillustrated with respect to FIG. 25 of U.S. Pat. No. 8,805,946, titled“SYSTEM AND METHOD FOR COMBINING CONTENT SITE VISITOR PROFILES,” whichwas previously incorporated by reference herein in its entirety.

Although the network 108 is shown as one connected network, the network108 can be subdivided into one or more separate networks which may notdirectly communicate with one another. For example, the analytics system130 can communicate with the tag management user system 104 via aseparate and different network from the network that the tag server 120uses to communicate with the end user system 102.

While the present disclosure includes examples for an electroniccommerce site, the systems and methods described herein may be used forany content site, such as a social network site, for example.

The various illustrative logical blocks, modules, and algorithm stepsdescribed in connection with the embodiments disclosed herein can beimplemented as electronic hardware, computer software, or combinationsof both. To clearly illustrate this interchangeability of hardware andsoftware, various illustrative components, blocks, modules, and stepshave been described above generally in terms of their functionality.Whether such functionality is implemented as hardware or softwaredepends upon the particular application and design constraints imposedon the overall system. The described functionality can be implemented invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the disclosure.

The various illustrative logical blocks and modules described inconnection with the embodiments disclosed herein can be implemented orperformed by a machine, such as a general purpose processor, a digitalsignal processor (DSP), an application specific integrated circuit(ASIC), a field programmable gate array (FPGA) or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general purpose processor can be a microprocessor,but in the alternative, the processor can be a controller,microcontroller, or state machine, combinations of the same, or thelike. A hardware processor can include electrical circuitry or digitallogic circuitry configured to process computer-executable instructions.In another embodiment, a processor includes an FPGA or otherprogrammable device that performs logic operations without processingcomputer-executable instructions. A processor can also be implemented asa combination of computing devices, e.g., a combination of a DSP and amicroprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration. A computing environment can include any type of computersystem, including, but not limited to, a computer system based on amicroprocessor, a mainframe computer, a digital signal processor, aportable computing device, a device controller, or a computationalengine within an appliance, to name a few.

The steps of a method, process, or algorithm described in connectionwith the embodiments disclosed herein can be embodied directly inhardware, in a software module stored in one or more memory devices andexecuted by one or more processors, or in a combination of the two. Asoftware module can reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of non-transitory computer-readable storagemedium, media, or physical computer storage known in the art. An examplestorage medium can be coupled to the processor such that the processorcan read information from, and write information to, the storage medium.In the alternative, the storage medium can be integral to the processor.The storage medium can be volatile or nonvolatile. The processor and thestorage medium can reside in an ASIC.

Conditional language used herein, such as, among others, “can,” “might,”“may,” “e.g.,” and the like, unless specifically stated otherwise, orotherwise understood within the context as used, is generally intendedto convey that certain embodiments include, while other embodiments donot include, certain features, elements or states. Thus, suchconditional language is not generally intended to imply that features,elements or states are in any way required for one or more embodimentsor that one or more embodiments necessarily include logic for deciding,with or without author input or prompting, whether these features,elements or states are included or are to be performed in any particularembodiment. The terms “comprising,” “including,” “having,” and the likeare synonymous and are used inclusively, in an open-ended fashion, anddo not exclude additional elements, features, acts, operations, and soforth. Also, the term “or” is used in its inclusive sense (and not inits exclusive sense) so that when used, for example, to connect a listof elements, the term “or” means one, some, or all of the elements inthe list. Further, the term “each,” as used herein, in addition tohaving its ordinary meaning, can mean any subset of a set of elements towhich the term “each” is applied.

While the above detailed description has shown, described, and pointedout novel features as applied to various embodiments, it will beunderstood that various omissions, substitutions, and changes in theform and details of the devices or algorithms illustrated can be madewithout departing from the spirit of the disclosure. As will berecognized, certain embodiments described herein can be embodied withina form that does not provide all of the features and benefits set forthherein, as some features can be used or practiced separately fromothers.

What is claimed is:
 1. A system comprising: non-transitory physicalcomputer storage; and a hardware processor configured to: access atemplate object, the template object comprising a prompt, a firstidentifier indicative of a home page attribute, and a second identifierindicative of an instruction set, wherein the home page attribute isassociated with a tag object capable of gathering first interaction dataindicative of end user interactions with a content page, and wherein theinstruction set comprises an operator and a first operand comprising thefirst identifier; present the prompt in a user interface, the promptcomprising textual information requesting input of the home pageattribute; receive, via the user interface, a user input comprising afirst value for the home page attribute; generate a home pageconfiguration from a property of the home page attribute and the firstvalue; store the home page configuration in the non-transitory physicalcomputer storage; determine, using the first identifier, a second valuefor the first operand, the second value corresponding to the firstvalue; determine, using the instruction set, that the operator issatisfied by the second value that indicates a home page visit; andgenerate second interaction data by assigning a trait to the firstinteraction data, the trait indicating a home page visitor.
 2. Thesystem of claim 1, wherein the template object further comprises a firstinput comprising a third identifier, and wherein the hardware processoris configured to: determine that the third identifier corresponds to asecond attribute; determine that a data value of the second attribute isassigned; access a pre-existing value for the data value of the secondattribute; and present the pre-existing value in the user interface. 3.The system of claim 1, wherein the home page configuration correspondsto a portion of a uniform resource locator, and wherein the first valuecomprises a textual string for the portion of the uniform resourcelocator.
 4. The system of claim 1, wherein the operator comprises atleast one of: exists, contains, equals, equals ignore case, or containsignore case.
 5. The system of claim 1, wherein the instruction setfurther comprises a boolean condition.
 6. The system of claim 1, whereinan output of the template object comprises a plurality of attributes. 7.A method comprising: under control of one or more hardware processors:accessing a template object, the template object comprising a prompt, afirst identifier indicative of a first template attribute, and a secondidentifier indicative of an instruction set, wherein the first templateattribute is associated with a tag object capable of gathering firstinteraction data indicative of end user interactions with a contentpage, and wherein the instruction set comprises an operator, a firstoperand, and a second operand comprising the first identifier;presenting the prompt in a user interface, the prompt comprising textualinformation requesting input of the first template attribute; receiving,via the user interface, a user input comprising a first value for thefirst template attribute; determining, using the first identifier, asecond value for the second operand, the second value corresponding tothe first value; determining, using the instruction set, that theoperator is satisfied by the first operand and the second value; andgenerating second interaction data by assigning a trait to the firstinteraction data, the trait indicating behavior of the end userinteractions with the content page.
 8. The method of claim 7, whereinthe template object further comprises a first input comprising a thirdidentifier, the method further comprising: determining that the thirdidentifier corresponds to a second attribute; determining that a datavalue of the second attribute is assigned; accessing a pre-existingvalue for the data value of the second attribute; and presenting thepre-existing value in the user interface.
 9. The method of claim 7,wherein an output of the template object comprises a plurality ofattributes.
 10. The method of claim 7, wherein a format of the templateobject comprises a JavaScript Object Notation (JSON) data format. 11.The method of claim 7, wherein the second value corresponds to an enduser's browser type, an end user's browser version, an end user'scomputing device, an end user's operating system, an end user's averagevisit duration in minutes, an end user's average number of visits, or aview count of content site pages.
 12. The method of claim 7, wherein thetrait corresponds to a first visitor, a frequent visitor, or a windowshopper.
 13. The method of claim 7, further comprising: presenting, inthe user interface, a workflow as defined by the template object, theworkflow comprising a series of prompts.
 14. A system comprising:non-transitory physical computer storage; and a hardware processorconfigured to: access a template object, the template object comprisinga prompt, a first identifier indicative of a first template attribute,and a second identifier indicative of an instruction set, wherein thefirst template attribute is associated with a tag object capable ofgathering first interaction data indicative of end user interactionswith a content page, and wherein the instruction set comprises anoperator and a first operand comprising the first identifier; presentthe prompt in a user interface, the prompt comprising textualinformation requesting input of the first template attribute; receive,via the user interface, a user input comprising a first value for thefirst template attribute; determine, using the first identifier, asecond value for the first operand, the second value corresponding tothe first value; determine, using the instruction set, that the operatoris satisfied by the second value; and generate second interaction databy assigning a trait to the first interaction data, the trait indicatingbehavior of the end user interactions with the content page.
 15. Thesystem of claim 14, wherein the template object further comprises afirst input comprising a third identifier, and wherein the hardwareprocessor is configured to: determine that the third identifiercorresponds to a second attribute; determine that a data value of thesecond attribute is assigned; access a pre-existing value for the datavalue of the second attribute; and present the pre-existing value in theuser interface.
 16. The system of claim 14, wherein the second valuecorresponds to an end user's browser type, an end user's browserversion, an end user's computing device, an end user's operating system,an end user's average visit duration in minutes, an end user's averagenumber of visits, or a view count of content site pages.
 17. The systemof claim 14, wherein the trait corresponds to a first visitor, afrequent visitor, or a window shopper.
 18. The system of claim 14,wherein the instruction set further comprises a second operand, andwherein the hardware processor is configured to apply the operator tothe second operand to determine that the operator is satisfied.
 19. Thesystem of claim 18, wherein the operator comprises a between operator.20. The system of claim 14, wherein the template object furthercomprises instructions that configure a visual presentation of theprompt in the user interface.